API version 2013-04-01 of the Amazon Route 53 SDK configuration.

The hosted zone doesn't have any DNSSEC resources.

The specified hosted zone is a public hosted zone, not a private hosted zone.

The key-signing key (KSK) that you specified can't be deactivated because it's the only KSK for a currently-enabled DNSSEC. Disable DNSSEC signing, or add or enable another KSK.

The specified key-signing key (KSK) doesn't exist.

There is no DNS query logging configuration with the specified ID.

The hosted zone contains resource records that are not SOA or NS records.

The input is not valid.

You can create a hosted zone that has the same name as an existing hosted zone (example.com is common), but there is a limit to the number of hosted zones that have the same name. If you get this error, Amazon Route 53 has reached that limit. If you own the domain name and Route 53 generates this error, contact Customer Support.

The VPC that you specified is not authorized to be associated with the hosted zone.

The value of HealthCheckVersion in the request doesn't match the value of HealthCheckVersion in the health check.

A reusable delegation set with the specified ID does not exist.

Amazon Route 53 doesn't support the specified geographic location. For a list of supported geolocation codes, see the GeoLocation data type.

The KeyManagementServiceArn that you specified isn't valid to use with DNSSEC signing.

The hosted zone you're trying to create already exists. Amazon Route 53 returns this error when a hosted zone has already been created with the specified CallerReference.

The specified domain name is not valid.

The key-signing key (KSK) status isn't valid or another KSK has the status INTERNAL_FAILURE.

The VPC that you're trying to disassociate from the private hosted zone is the last VPC that is associated with the hosted zone. Amazon Route 53 doesn't support disassociating the last VPC from a hosted zone.

This error code is not in use.

A traffic policy that has the same value for Name already exists.

The resource you're trying to access is unsupported on this Amazon Route 53 endpoint.

This exception contains a list of messages that might contain one or more error messages. Each error message indicates one error in the change batch.

The format of the traffic policy document that you specified in the Document element is not valid.

No traffic policy instance exists with the specified ID.

This traffic policy instance can't be created because the current account has reached the limit on the number of traffic policy instances.

For information about default limits, see Limits in the Amazon Route 53 Developer Guide.

For information about how to get the current limit for an account, see GetAccountLimit.

To request a higher limit, create a case with the Amazon Web Services Support Center.

Amazon Route 53 doesn't have the permissions required to create log streams and send query logs to log streams. Possible causes include the following:

• There is no resource policy that specifies the log group ARN in the value for Resource.
• The resource policy that includes the log group ARN in the value for Resource doesn't have the necessary permissions.
• The resource policy hasn't finished propagating yet.
• The Key management service (KMS) key you specified doesn’t exist or it can’t be used with the log group associated with query log. Update or provide a resource policy to grant permissions for the KMS key.

There is no CloudWatch Logs log group with the specified ARN.

This operation can't be completed either because the current account has reached the limit on reusable delegation sets that it can create or because you've reached the limit on the number of Amazon VPCs that you can associate with a private hosted zone. To get the current limit on the number of reusable delegation sets, see GetAccountLimit. To get the current limit on the number of Amazon VPCs that you can associate with a private hosted zone, see GetHostedZoneLimit. To request a higher limit, create a case with the Amazon Web Services Support Center.

The key-signing key (KSK) name that you specified isn't a valid name.

You've already created a key-signing key (KSK) with this name or with the same customer managed customer master key (CMK) ARN.

You can create only one query logging configuration for a hosted zone, and a query logging configuration already exists for this hosted zone.

There is already a traffic policy instance with the specified ID.

The limit on the number of requests per second was exceeded.

The key-signing key (KSK) is specified in a parent DS record.

The specified VPC and hosted zone are not currently associated.

You've reached the limit for the number of key-signing keys (KSKs). Remove at least one KSK, and then try again.

This traffic policy can't be created because the current account has reached the limit on the number of traffic policies.

For information about default limits, see Limits in the Amazon Route 53 Developer Guide.

To get the current limit for an account, see GetAccountLimit.

To request a higher limit, create a case with the Amazon Web Services Support Center.

The specified delegation contains associated hosted zones which must be deleted before the reusable delegation set can be deleted.

The health check you're attempting to create already exists. Amazon Route 53 returns this error when you submit a request that has the following values:

• The same value for CallerReference as an existing health check, and one or more values that differ from the existing health check that has the same caller reference.
• The same value for CallerReference as a health check that you created and later deleted, regardless of the other settings in the request.

The specified HostedZone can't be found.

This traffic policy version can't be created because you've reached the limit of 1000 on the number of versions that you can create for the current traffic policy.

To create more traffic policy versions, you can use GetTrafficPolicy to get the traffic policy document for a specified traffic policy version, and then use CreateTrafficPolicy to create a new traffic policy using the traffic policy document.

No traffic policy exists with the specified ID.

One or more traffic policy instances were created by using the specified traffic policy.

The VPC ID that you specified either isn't a valid ID or the current account is not authorized to access this VPC.

A delegation set with the same owner and caller reference combination has already been created.

The cause of this error depends on the operation that you're performing:

• Create a public hosted zone: Two hosted zones that have the same name or that have a parent/child relationship (example.com and test.example.com) can't have any common name servers. You tried to create a hosted zone that has the same name as an existing hosted zone or that's the parent or child of an existing hosted zone, and you specified a delegation set that shares one or more name servers with the existing hosted zone. For more information, see CreateReusableDelegationSet.
• Create a private hosted zone: A hosted zone with the specified name already exists and is already associated with the Amazon VPC that you specified.
• Associate VPCs with a private hosted zone: The VPC that you specified is already associated with another hosted zone that has the same name.

This health check can't be created because the current account has reached the limit on the number of active health checks.

For information about default limits, see Limits in the Amazon Route 53 Developer Guide.

For information about how to get the current limit for an account, see GetAccountLimit. To request a higher limit, create a case with the Amazon Web Services Support Center.

You have reached the maximum number of active health checks for an Amazon Web Services account. To request a higher limit, create a case with the Amazon Web Services Support Center.

A reusable delegation set with the specified ID does not exist.

No health check exists with the specified ID.

Your hosted zone status isn't valid for this operation. In the hosted zone, change the status to enable DNSSEC or disable DNSSEC.

The value that you specified to get the second or subsequent page of results is invalid.

You've created the maximum number of authorizations that can be created for the specified hosted zone. To authorize another VPC to be associated with the hosted zone, submit a DeleteVPCAssociationAuthorization request to remove an existing authorization. To get a list of existing authorizations, submit a ListVPCAssociationAuthorizations request.

This operation can't be completed either because the current account has reached the limit on the number of hosted zones or because you've reached the limit on the number of hosted zones that can be associated with a reusable delegation set.

For information about default limits, see Limits in the Amazon Route 53 Developer Guide.

To get the current limit on hosted zones that can be created by an account, see GetAccountLimit.

To get the current limit on hosted zones that can be associated with a reusable delegation set, see GetReusableDelegationSetLimit.

To request a higher limit, create a case with the Amazon Web Services Support Center.

If Amazon Route 53 can't process a request before the next request arrives, it will reject subsequent requests for the same hosted zone and return an HTTP 400 error (Bad request). If Route 53 returns this error repeatedly for the same request, we recommend that you wait, in intervals of increasing duration, before you try the request again.

You're trying to associate a VPC with a public hosted zone. Amazon Route 53 doesn't support associating a VPC with a public hosted zone.

No hosted zone exists with the ID that you specified.

Associating the specified VPC with the specified hosted zone has not been authorized.

You tried to update a traffic policy instance by using a traffic policy version that has a different DNS type than the current type for the instance. You specified the type in the JSON document in the CreateTrafficPolicy or CreateTrafficPolicyVersionrequest.

Another user submitted a request to create, update, or delete the object at the same time that you did. Retry the request.

The specified delegation set has already been marked as reusable.

A key-signing key (KSK) with ACTIVE status wasn't found.

The hosted zone nameservers don't match the parent nameservers. The hosted zone and parent must have the same nameservers.

A change with the specified change ID does not exist.

Parameter name is not valid.

Polls GetChange every 30 seconds until a successful state is reached. An error is returned after 60 failed checks.

See: newCreateReusableDelegationSet smart constructor.

Create a value of CreateReusableDelegationSet with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:hostedZoneId:CreateReusableDelegationSet', createReusableDelegationSet_hostedZoneId - If you want to mark the delegation set for an existing hosted zone as reusable, the ID for that hosted zone.

$sel:callerReference:CreateReusableDelegationSet', createReusableDelegationSet_callerReference - A unique string that identifies the request, and that allows you to retry failed CreateReusableDelegationSet requests without the risk of executing the operation twice. You must use a unique CallerReference string every time you submit a CreateReusableDelegationSet request. CallerReference can be any unique string, for example a date/time stamp.

See: newCreateReusableDelegationSetResponse smart constructor.

Create a value of CreateReusableDelegationSetResponse with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:httpStatus:CreateReusableDelegationSetResponse', createReusableDelegationSetResponse_httpStatus - The response's http status code.

$sel:delegationSet:CreateReusableDelegationSetResponse', createReusableDelegationSetResponse_delegationSet - A complex type that contains name server information.

$sel:location:CreateReusableDelegationSetResponse', createReusableDelegationSetResponse_location - The unique URL representing the new reusable delegation set.

A request for the number of health checks that are associated with the current Amazon Web Services account.

See: newGetHealthCheckCount smart constructor.

Create a value of GetHealthCheckCount with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

A complex type that contains the response to a GetHealthCheckCount request.

See: newGetHealthCheckCountResponse smart constructor.

Create a value of GetHealthCheckCountResponse with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:httpStatus:GetHealthCheckCountResponse', getHealthCheckCountResponse_httpStatus - The response's http status code.

$sel:healthCheckCount:GetHealthCheckCountResponse', getHealthCheckCountResponse_healthCheckCount - The number of health checks associated with the current Amazon Web Services account.

A complex type that contains information about the request to create a hosted zone.

See: newGetHostedZoneLimit smart constructor.

Create a value of GetHostedZoneLimit with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:type':GetHostedZoneLimit', getHostedZoneLimit_type - The limit that you want to get. Valid values include the following:

• MAX_RRSETS_BY_ZONE: The maximum number of records that you can create in the specified hosted zone.
• MAX_VPCS_ASSOCIATED_BY_ZONE: The maximum number of Amazon VPCs that you can associate with the specified private hosted zone.

$sel:hostedZoneId:GetHostedZoneLimit', getHostedZoneLimit_hostedZoneId - The ID of the hosted zone that you want to get a limit for.

A complex type that contains the requested limit.

See: newGetHostedZoneLimitResponse smart constructor.

Create a value of GetHostedZoneLimitResponse with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:httpStatus:GetHostedZoneLimitResponse', getHostedZoneLimitResponse_httpStatus - The response's http status code.

$sel:limit:GetHostedZoneLimitResponse', getHostedZoneLimitResponse_limit - The current setting for the specified limit. For example, if you specified MAX_RRSETS_BY_ZONE for the value of Type in the request, the value of Limit is the maximum number of records that you can create in the specified hosted zone.

$sel:count:GetHostedZoneLimitResponse', getHostedZoneLimitResponse_count - The current number of entities that you have created of the specified type. For example, if you specified MAX_RRSETS_BY_ZONE for the value of Type in the request, the value of Count is the current number of records that you have created in the specified hosted zone.

A complex type that contains information about the request to associate a VPC with a private hosted zone.

See: newAssociateVPCWithHostedZone smart constructor.

Create a value of AssociateVPCWithHostedZone with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:comment:AssociateVPCWithHostedZone', associateVPCWithHostedZone_comment - Optional: A comment about the association request.

$sel:hostedZoneId:AssociateVPCWithHostedZone', associateVPCWithHostedZone_hostedZoneId - The ID of the private hosted zone that you want to associate an Amazon VPC with.

Note that you can't associate a VPC with a hosted zone that doesn't have an existing VPC association.

$sel:vpc:AssociateVPCWithHostedZone', associateVPCWithHostedZone_vpc - A complex type that contains information about the VPC that you want to associate with a private hosted zone.

A complex type that contains the response information for the AssociateVPCWithHostedZone request.

See: newAssociateVPCWithHostedZoneResponse smart constructor.

Create a value of AssociateVPCWithHostedZoneResponse with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:httpStatus:AssociateVPCWithHostedZoneResponse', associateVPCWithHostedZoneResponse_httpStatus - The response's http status code.

$sel:changeInfo:AssociateVPCWithHostedZoneResponse', associateVPCWithHostedZoneResponse_changeInfo - A complex type that describes the changes made to your hosted zone.

A complex type that contains information about the traffic policy that you want to create.

See: newCreateTrafficPolicy smart constructor.